-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Display summary data per deployment #299
Conversation
If an admin exec'd into a pod, the summary data will be inconsistent across pods, there would be no to tell which pod was exec'd into to perform some operations (which process was triggered in which pod). Won't hamper the summary much but just something that should be considered once. |
Super! This is very useful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR works only for deployments but not for stateful sets and other resource types.
- Modified summary code to have deployment name and deployment type as a parameter - Updated code to display summary per resource type if podname is not mentioned Signed-off-by: Vishnu Soman <[email protected]>
Updated OutputsSummary Help
Summary without any input
Summary with filter type as
Summary with filter type
Summary with podname
Summary with wrong filter type and workload name
Summary as JSON output
|
karmor summary has been deprecated |
Related PR's
This PR depends on the above-mentioned PR and can be marked as ready once it is merged. With this change, the summary data will be displayed per deployment by default unless the user explicitly uses the
-p
flag and mention a pod name.Sample Output
karmor summary
with podnamekarmor summary
with deployment namekarmor summary
without any input